\chapter{Risks}
\label{cap:Risks}
\section{Risks Analiys}


\begin{comment}
	Ma quanto e' nerd il package comment!!! xD

	Per l'analisi dei rischi ci siamo affidati completamente alla nostra esperienza, non avendo alcuno strumento efficacie per stimarlo, ne essendo d'aiuto le analisi svolte in precedenza nell'ambito dello stesso progetto.
	Principalmente abbiamo escluso tutti i rischi estremi, che sono poco probabili e non sono da considerare nell'ambityo di questro progetto, vista la limitetezza temporale e le poche persone in gioco.
	Abbiamo tralasciato anche i rischi più banali, in quanto sono aspetti che non necessitano di nessuna organizzazione preventiva, e sono tenuti in conto nella nosramle stima del processo di sviluppo.
	Abbiamo quindi analizzato i rischi più significativi, e descritto in breve i modi per risolverli. la maggior parte sono autoesplicativi, tuttavia, abbiamo assegnato la priorità della soluzione di determinati problemi alle persone del gruppo che sono più competenti e capaci per affrontarli.
\end{comment}

For what concerns the risks analysis, we entirely relied on the experience coming from our past project, since we had not any efficient tool to estimate it
and since that we had any risk data about that project. \\
As the most extreme risks has little probability to happen, we excluded them from our analysis. Furthermore project has to be developed in very few time so this probability is even lower.\\
We left out trivial risks as well, since they do not need any preventive organization, and they are implicitly considered in the normal evaluation of the development process. \\
Focusing on the main risks we have briefly described the ways we intend to solve them.
The most of these problems are self-explanatory, anyway, for each of them, we have chosen a person in the team to handle it, according to his personal skills and abilities.
\newline



\section{Risks and Possible Solutions}
\begin{itemize}
	\item \textbf{No time for advanced functionalities \ldots}\\
	It is possible we spend lot of time in doing other essential task for the project.Thus if time is essentially critical the best thing to do is to skip and do not implement advanced functionalities for the first relase. \\
	\noindent
	 \item \textbf{Problems with the envirorment \ldots} \\
	 Probably we should face problems with envirorment tools. In this situation we are supposed to delay other tasks and ask tutors\\
	\noindent
	\item \textbf{ Problems with repository \ldots} \\
	 Sometimes it's possible to get in trouble with the online repository, in these cases we are going to move Dave to repository recovery task. \\
	\noindent
	\item \textbf{ Problems with COTS (e.g. mySql if needed ) \ldots}  \\
	 These kind of problems are similar to the envirorment tools ones. We are supposed to ask tutors or google for solution.In case of hard problems it would be essential to meet together and solve them.\\
	\noindent
	\item \textbf{Problems with bad design  \ldots} \\
	 If we relize we did a bad design, it's foundamental to stop all tasks and refactor the whole project.\\
	\noindent
	\item \textbf{Problems of lack of time of group members \ldots} \\
	 In case of lack of time issues basically we'll redistribute time or we'll get in 'hero mode' (do the more we can). \\
	\noindent
	\item \textbf{ Problems with strange bugs \ldots} \\
	 Bug problems will be generally fixed by Edo performing a step-by-step simulation in order to find bugs origin using the debugging tools (Obviously this task could be attempt by every team member and all together if needed).
\end{itemize}
